When removing a parent node via removeCells, its children are not recursively removed from the model, leaving orphan nodes. Subsequent re-creation of nodes with the same IDs results in apparent duplicates.

Root Cause

collection.removeCells sets cell.model = null (via the removed event → onCellRemoved) before calling cell.remove(). Inside remove(), eachChild() calls getChildren() which requires this.model to resolve child IDs — returning null when model is already null. Children are silently skipped.

Changes

• src/model/cell.ts — remove(): Fall back to _children cache when getChildren() returns null due to model being null, ensuring children are still recursively removed:

  const children = this.getChildren() ?? (this._children ? [...this._children] : null)
  if (children) {
    children.forEach((child) => child.remove(options))
  }

• src/model/cell.ts — remove(): Keep parent._children in sync when directly mutating parent.store (bypassing setChildren()), so the fallback cache is not stale.
• __tests__/model/cell.spec.ts: Add test that simulates the actual collection.removeCells flow (model set to null before remove() is called) and asserts children are removed from the model.

• Fixes 🐞3.1.6、3.1.5的删除节点removeCells方法有问题（删除子节点以后，重新创建更新子节点，出现重复节点），3.1.4正常，麻烦排查一下 #5032

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.